Slider

Sliders are visual controls that you can operate with your mouse. A slider can be wired into any input port to provide a numeric value. You can specify the range of values that is produced by the slider as well as control the increments between values and whether "tick marks" are visible on the slider.

Similar to any other nodes, the slider can be set its technique from the available techniques. The required input port varies according to the current technique selected. You can pin desired ports to include slider controls.

The below example illustrate the effect of two sliders applied to a line node created using the ByStartPointDirectionLength technique. It essentially requires the following inputs:

StartPoint — wired from reference point1 node to support the line.
Direction — borrowed from baseCS node's Y direction.
Length — wired from slider01 node, that controls the length of the line.

Additionally, the Color input is also pinned for line1 to visualise the effect .

Color — wired from slider2 node, that controls the length of the line.

line1 Length: 6 units, Color: 5

The Length and Color of line01 are controlled by slider1 and slider2 respectively. The length of the line1 changes along Y as when the handle on slider1 is dragged, and the color changes when the handle position on slider2 is shifted.

line1 Length: 10 units, Color: 1

Resolution

Resolution is the increment of the value that can be specified by users. As you move the slider, the value jumps in the specified increments. This is useful if you want to create a variable defining the number of elements and only want it to be whole values to reflect the count of complete elements. Then the step size would be set to "1" to limit the range to whole values only.

This is useful when a slider controls a very large complex model and it is impossible to compute every new configuration between 1 and 10 at a .01 increment. When this happens GenerativeComponents will slow down and your computer's performance will suffer. Changing the step size allows GenerativeComponents to compute fewer configurations. With a simple small model this may not be necessary, but as the model develops more complexity increasing the step size may become necessary.